Centralized management of motor vehicle software applications and services

ABSTRACT

In one example, a network device stores a mapping of application operation modes to vehicle conditions such as a first condition of the vehicle powered but not moving and a second condition of the vehicle moving. The network device receives a wirelessly transmitted request for a particular application to utilize an interface powered by the vehicle. The network device compares an application identifier specified by the received request to the mapping. The network device then identifies a portion of the vehicle interface according to the comparison and signals control software on the vehicle to grant the particular application access to only the identified portion of the vehicle interface itself. The application can reside on the mobile device and utilize the vehicle interface as an extended interface, or the application can reside on the vehicle.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/777,989 filed on May 11, 2010, entitled: CENTRALIZED MANAGEMENT OFMOTOR VEHICLE SOFTWARE APPLICATIONS AND SERVICES, which is acontinuation-in-part of U.S. patent application Ser. No. 12/729,207filed on Mar. 22, 2010, entitled: CENTRALIZED MANAGEMENT OF MOTORVEHICLE SOFTWARE APPLICATIONS AND SERVICES, which is a non-provisionalof U.S. Provisional Application No. 61/252,066 filed on Oct. 15, 2009,entitled: CENTRALIZED MANAGEMENT OF MOTOR VEHICLE SOFTWARE APPLICATIONSAND SERVICES and U.S. Provisional Application No. 61/260,781 filed onNov. 12, 2009, entitled: CENTRALIZED MANAGEMENT OF MOTOR VEHICLESOFTWARE APPLICATIONS AND SERVICES, each of which is herein incorporatedby reference in its entirety.

COPYRIGHT NOTICE

© 2010 Airbiquity, Inc. A portion of the disclosure of this patentdocument contains material which is subject to copyright protection. Thecopyright owner has no objection to the facsimile reproduction by anyoneof the patent document or the patent disclosure, as it appears in thePatent and Trademark Office patent file or records, but otherwisereserves all copyright rights whatsoever. 37 CFR §1.71(d).

BACKGROUND OF THE INVENTION

A motor vehicle can be equipped with a “head unit” having a userinterface. The user interface can include various resource componentssuch as a screen, speakers, a microphone, a touch screen and/or keypad,etc.

Smart phones or other mobile phones can download various applicationsthat operate on the phone. A user can utilize a user interface of thephone to control the application and/or utilize the application in someway (such as watching the visual display or listening to the audiooutput).

Extending applications from the mobile phone to the head unit has becomea popular feature offered by various service providers and vehiclemanufacturers. As a result, the user can take advantage of better userinterface components offered by the head unit (e.g. a larger screen andhigher quality audio output). It is desirable to provide a mechanism tocontrol, manage, and arbitrate the extension of mobile phoneapplications operating on the head unit utilizing the service controllogic available in a remote server.

Vehicles can also be manufactured with components that allow theapplications to be installed on the vehicle itself (as opposed to beinginstalled on a mobile device). It is desirable to control, manage, andarbitrate the use of the vehicle interface by these applications aswell.

SUMMARY OF THE INVENTION

The following is a summary of the invention in order to provide a basicunderstanding of some aspects of the invention. This summary is notintended to identify key/critical elements of the invention or todelineate the scope of the invention. Its sole purpose is to presentsome concepts of the invention in a simplified form as a prelude to themore detailed description that is presented later.

In one example, a network device stores a mapping of applicationoperation modes to vehicle conditions such as a first condition of thevehicle powered but not moving and a second condition of the vehiclemoving. The network device receives a wirelessly transmitted request(sent by either a wireless transmitter of the vehicle or of a mobiledevice coupled to the vehicle) for a particular application to utilizean interface powered by the vehicle. The network device compares anapplication identifier specified by the received request to the mapping.The network device then identifies a portion of the vehicle interfaceaccording to the comparison and signals control software on the vehicleto grant the particular application access to only the identifiedportion of the vehicle interface. The application can reside on themobile device and utilize the vehicle interface as an extendedinterface, or the application can reside on the vehicle itself.Additional aspects and advantages of this invention will be apparentfrom the following detailed description of preferred embodiments, whichproceeds with reference to the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system to control the use of a head unit as anextended interface for a phone application in a safe and intelligentmanner.

FIG. 2A illustrates a flow chart showing operation of the software 32 ofFIG. 1.

FIG. 2B illustrates a flow chart showing a contention scheme that can beused by the software 32 of FIG. 1.

FIG. 3 illustrates a flow chart showing operation of the software 30A-Bof FIG. 1.

FIG. 4 illustrates a system to select and distribute applications to avehicle in a safe and intelligent manner.

FIG. 5 illustrates a flow chart showing operation of the software ofFIG. 4.

FIG. 6 illustrates more detail of the system shown in FIGS. 4-5.

FIG. 7 illustrates a system to select and distribute applications to avehicle in a safe and intelligent manner according to user preferences.

FIG. 8 illustrates a flow chart showing operation of the software ofFIG. 7.

FIG. 9 illustrates more detail of the system shown in FIGS. 7-8.

FIG. 10 illustrates a system to select a head unit graphical interfaceaccording to a configuration of the head unit.

FIG. 11 illustrates a system to generate and send remote computingapprovals to the head unit.

FIG. 12 illustrates a system to push graphical user interface updates tothe head unit in response to the mobile device generating a request fora new application or the user web portal selecting a new application.

FIG. 13A illustrates a flow chart showing pre-operation of a parentalcontrol scheme.

FIG. 13B illustrates a flow chart showing operation of the parentalcontrol scheme.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

In one example, a user couples a phone to a motor vehicle head unitusing a wired or wireless connection for the purpose of using the headunit as an extended interface for the phone. The user may be permittedto control an application on the phone using the interface of the headunit, depending on a determination via a remote server as described inthe next paragraph. Similarly, the user may be permitted to watch orlisten to an output of the application over the interface of the headunit, depending on a determination via a remote server as described inthe next paragraph.

Novel client control software on the phone and the head unit interfaceswith novel server control software on a remote server over a wirelessconnection extending from the phone. The client control softwareidentifies a phone application to utilize the head unit as an extendedinterface. The server control software compares the identified phoneapplication to one or more databases accessible by the remote server.Based on the comparison, the server control software determines whetherthe identified application will be permitted to utilize the head unit asan extended interface, and if so, which components of the head unitinterface will be permitted to be used by the application. The servercontrol software signals the client control software to control thephone and head unit according to the determination. Accordingly, anyutilization of the head unit as an extended interface can be controlledin a safe and intelligent manner.

FIG. 1 illustrates a system to control the use of a head unit as anextended interface for a phone application in a safe and intelligentmanner.

The system 100 includes software 30A and 30B configured on,respectively, a mobile phone 20 (or other mobile device) and head unit21 (or other interface powered by a motor vehicle such as a userinterface integrated with a steering wheel or a user interfaceintegrated with a seat back). The software 30A and 30B interfaces withthe software 32 configured on a remote server 22 to regulate and controlwhen and how applications 40 operating on the phone 20 access I/Oresources 1-4 of the head unit 21.

FIG. 2A illustrates a flow chart showing operation of the software 32 ofFIG. 1.

In block 201, the software 32 receives a request for a particularapplication 40 on the phone 20 to utilize the interface (including input24 resources 1-2 and output 25 resources 3-4) of the head unit 21. Therequest includes a user identifier corresponding to the user of themotor vehicle and/or head unit 21, an application identifiercorresponding to the particular application 40, and vehicle statusinformation. The user identifier could be an identifier provided by theuser when the control software 30A was first activated in the mobilephone 100, user's phone number, etc.

In block 202, the software 32 authenticates the user. This can includedetermining whether the user identified by the user identifier matches adatabase 11 of subscribers for the service of extending the interface ofthe phone 20 using the head unit 21. If the user is not authenticated indiamond 203, then in block 204A the software 32 signals the software30A/B to block access by the application 40 to the head unit 21. Itshould be understood that the system 100 can be configured so that block202 is optional.

Otherwise, if the user is authenticated, then in block 204B the software32 authenticates the application 40 by comparing the applicationidentifier to a list 12 of applications (also referred to as awhitelist). This list 12 can be compared by version number such that oneparticular version of an application 40 can be identified on the listwhile a different version is excluded. If the particular application 40(or particular version) is not on the list 12 in diamond 205, then inblock 204A the software 32 signals the software 30A-B to block access bythe application 40 to the head unit 21.

Otherwise, if the application 40 is authenticated, then in block 206 thesoftware 32 compares the application identifier and the current vehiclestatus information to a mapping 15 of application operation modes. Asshown, the mapping 15 can have an entry 17 for each application 40 ofthe list 12. Each entry 17 includes a mapping that is particularized forthe corresponding application 40. For example, an entry 17 forapplication A maps the vehicle status “vehicle moving≦than X” toresources 1, 2, and 4 (namely application A will be permitted to accessthe only the screen 1, the speaker 2, and microphone 4 under thisvehicle condition) whereas the entry 17 for application C maps thevehicle status “vehicle moving≦than X” to only resources 2 and 4 (namelyapplication C will be permitted to access the speaker 2 and microphone4). One real world example might be a navigation application A and avideo game application C, where even when a passenger is present thesystem 100 will not allow the video game application C to be displayedon the head unit 21 screen 1 as this is deemed to be too much of adistraction for a driver whereas the navigation application A can bedisplayed on the head unit 21 screen 1. Another real world applicationcan be a vehicle with a plurality of interfaces, such as a head unit anda display attached to the back of a seat. An application can be grantedaccess to the back seat display under conditions where the sameapplication would not be granted access to the head unit.

It should be understood that, in other examples, the mapping 15X can bestored on the mobile phone 20. In this case, the comparison described inthe previous paragraph can be performed by the control software 30A. Insuch a case, the control software 30A checks the current vehicle statusby communicating with the head unit 21.

In block 207, the software 32 identifies a set of some or all of the I/Oresources of the head unit 21 according to the comparison. In block 208,the software 32 signals the remote software to provide the particularapplication 40 access to only those ones of the I/O resources 1-4 of theidentified set. In one example, such signaling can include controllingthe software 30A on the mobile phone 20 so that all access requests sentfrom the mobile phone 20 conform to the identified set of the I/Oresources. In another example, such signaling can include controllingthe software 30B on the head unit 21 to block access requests sent fromthe mobile phone 20 in any manner such as by simply disabling I/Oresources on the head unit 21. In yet other examples, such signaling caninclude controlling both the software 30A and the software 30B.

FIG. 2B illustrates a flow chart showing a contention scheme that can beused by the software 30B of FIG. 1. A contention scheme can be utilizedin addition to the scheme shown in FIG. 2A.

In block 209, the software 30B determines whether any of the I/Oresources of the identified set are currently in use. If none are in usein diamond 210, then in block 211A the software 30B provides theparticular application access to only those I/O resources of theidentified set.

Otherwise, if at least one of the resources of the set is in use, thenin block 211B the software 30B identifies a by-resource ranking 13 ofthe applications for each of the in-use resources of the identified set.This is shown in FIG. 1 where there is a ranking 13 for each resource1-4. In block 212, the software 30B compares the application identifierto the by-resource ranking(s) 13 to determine whether the application 40has priority for any of the in-use resources of the identified subset(the may be performed via signaling since the ranking 13 is shown on theremote server or the ranking may have been sent to the vehicle interfacein an earlier process). This comparison will indicate whether theapplication currently using a particular in-use resource is deemedhigher or lower priority than the requesting application for that in-useresource. In block 213, the software 30B provides the particularapplication 40 access to only those ones of the I/O resources 1-4 of theidentified set that are also not currently in use or are in use by alower priority application.

FIG. 3 illustrates a flow chart showing operation of the software 30A-Bof FIG. 1.

In block 301, the software 30A-B sends a request for a particularapplication 40 on the phone 20 to utilize the interface of the head unit21. In block 302, the software 30A-B receives back a signal indicatingwhether or not the application 40 is authorized to access the head unit21 at this time, and if so, an identification of which resources 1-4 canbe utilized. If the application 40 is not authorized in diamond 303,then in block 304A the software 30A-B outputs a notification that theapplication 40 is not authorized to access the head unit. Thisnotification could be output by the mobile phone 20 or the head unit 21,or both.

Otherwise, if the application 40 is authorized in diamond 303, then inblock 304B the software 30A-B controls the mobile phone 20 and the headunit 21 to cause the application 40 to be extended to the identifiedresources. If only a subset of possible resources for the application 40(from the respective mapping 17) are utilized due to a conflict, thenthe software 30A-B may generate a notification to alert the driver aboutthe lower priority application being suspended before activating thehigher priority application. In another example, if the resources arecurrently used by a lower priority application, software 30A-B canautomatically suspend/end the lower priority application and allow thehigher priority application to be activated using the requiredresources.

If it is determined that application 40 can be extended to the head-unit21, the server 22 can download corresponding “control panel” software tothe head unit to control the application 40. By having downloading thissoftware to the head unit 21 based on the application being requested, aservice provider can customize and update the “control panel”accordingly when new applications or update to existing applications areavailable. The head-unit can have a web-code renderer to display the“control panel” software.

Referring again to FIG. 1, the software 30A-B interfaces with thesoftware 32 over a wireless connection extending from the phone 20. Thiswireless connection can utilize a packet data connection (including butnot limited to GPRS, EDGE, EVDO, UTMS, WiMAX, WiFi, etc.), Short MessageService (SMS), or In-Band-Signaling modems on the mobile phone 20 andthe remote server 22 as described in U.S. Pat. Nos. 6,144,336;6,690,681; and 6,493,338.

Still referring to FIG. 1, it is noted that the mobile phone 20 cancouple to the head unit 21 by using a connection such as a USB,Bluetooth, or WiFi connection. These are just examples, however, and inother cases a different connection and/or protocol may be suitable forutilizing the interface of the head unit 21 for the application 40 ofthe phone 20.

It should be understood that the mapping 15 can have any vehiclestatuses and that the four illustrated examples are merely someexamples. For example, another vehicle status could be whether thevehicle is moving more than speed ‘X’ AND a passenger is present.

It should be understood the head unit 21 can include less than all theexample resources shown, or other resources that are not shown. Forexample, another possible I/O resource component is a text to speechcomponent.

In the illustrated example, a first application can be permitted toaccess a first subset of whichever resources are actually present on thehead unit 21 based on an intelligent decision by the system 100, while asecond different application can be permitted to access a second subsetof the resources, or even all of the resources.

It should be understood that the applications 40 can be ranked “byresource” as illustrated or there can be a single ranking including allthe applications 40. The system 100 is implemented with the “byresource” ranking as shown, but the concepts described herein could beimplemented in another system that ranks applications independently ofresource.

FIG. 4 illustrates a system to select and distribute applications to avehicle in a safe and intelligent manner.

One difference between the previously discussed system of FIG. 1 and thesystem of FIG. 4 is the install location for applications. Whereas theapplications A-C in the system 100 of FIG. 1 are installed and operatingon the mobile phone 20 (using the head unit 21 or other interfacepowered by the vehicle as an extended interface), the applications J-Lin the system 200 of FIG. 4 are installed on the head unit 221 or othercomponent powered by the vehicle. In system 200 of FIG. 4, the software230-232 enables a provider to select which applications can be installedon the head unit 221 and control distribution of the selectedapplications to the vehicle.

Before discussing the details of system 200 in the following paragraphs,it should be apparent that the structures and functions of system 100described in FIGS. 1-3 can be combined with the structures and functionsof system 200 (FIGS. 4-6) into a single system. For example, a singlesystem could include some applications installed on a mobile phone usingan interface of a vehicle as an extended interface and some applicationsinstalled on a component of the vehicle.

FIG. 5 illustrates a flow chart showing operation of the software ofFIG. 4.

In block 501, in response to the vehicle being powered up, the controlsoftware 230 sends a signal 244 to the server 222 indicating vehiclepower-up. The signal 244 can be sent over a local connection such as aUSB or Bluetooth connection to be relayed by the mobile device 220 overa wireless telecommunications network.

In block 502, the software 232 checks a download directory 239(sometimes referred to as a “sandbox”) associated with the vehicle todetermine if there are any applications to be downloaded to the vehicle.A scheme for intelligently selecting applications that are present inthe download directory 239 will be discussed in detail later withreference to FIG. 6.

If the check by the software 232 indicates that the download directory239 includes at least one application, the process continues. For now,let it be assumed for the purposes of illustration that the downloaddirectory 239 includes applications 240 (J-L). Accordingly, in block 503the software 232 generates and sends signaling 245 to cause the IPgateway software 231 on the mobile phone 220 to operate as an IP gatewayfor forwarding applications to the head unit 221. In one example,signaling 245 includes communications to dynamically load the mobilephone 220 with the software 231 in response to the determination inblock 502 and cause the software 231 to operate thereon for the downloadto vehicle. The signaling 245 may not take place if the mobile phone 220is already loaded with the software 231 and ready for IP gatewayoperation. In other examples, the signaling 245 could originate from thecontrol software 230 on the head unit 221 in response to detectingvehicle power-up.

In block 504, the software 232 generates and sends IP packets 250 todownload the applications 240 onto the vehicle. The IP packets 250 arereceived by the mobile phone 220 and forwarded by operation of thesoftware 231 to the head unit 221. In block 505, the software 230receives the IP packets 230 and installs the applications 240 (J-L) onthe vehicle (installation can be on components of the head unit 221 orother vehicle components).

Thereafter, a user of the vehicle can operate the applications J-L usingthe head unit 221 as an interface. It should be understood that thesoftware 230 and 232 can operate according to any of the principlesdescribed in FIGS. 1-3. For example, the software 230 and 232 canregulate utilization of the I/O resources of the head unit 221 by theactive application(s) according to current vehicle status. As anotherexample, in systems where applications are installed on both the vehicleand a mobile device, the software 230 and 232 can include allapplications that utilize the vehicle interface in an applicationranking/priority table similar to the table 13 (FIG. 1).

In one example, the head unit 221 includes a web code renderer 299, forexample an HTML renderer, controlled via the software 230. The web coderenderer 299 is configured to display HTML code, but unlike a browser,does not allow a user to freely navigate to web locations. Specifically,the web code renderer 299 displays only applications allowed by theprovider, e.g. specified by the server 222.

It should be understood that the flow chart described above addressesupdating applications installed on the vehicle. The vehicle can also bepre-loaded with certain applications so that some of the applicationsinstalled on the vehicle are downloaded according to the flowchart whileothers are installed thereon during manufacturing.

Thus, based on the principles described above, vehicles can bemanufactured with none of the applications installed on the vehicle butinstead the applications can downloaded to the vehicles when the driversare present in the vehicles. The types of applications downloaded to thevehicles are governed by preferences defined in the network serverprovided by the drivers.

FIG. 6 illustrates more detail of the system shown in FIGS. 4-5.

It was previously explained that the server 222 includes a downloaddirectory 239 of applications waiting to be downloaded on a per-vehiclebasis. FIG. 6 illustrates the user web portals 601, 604, and 605 thatcan be involved in selection of the applications in the downloaddirectory 239 and describes an example use of these web portals 601,604, and 605.

A provider such as an OEM of the vehicle operates the web portal 601.Using an interface such as a computing terminal 625, the providercontrols an application selection portion 608 of the web portal 601 withcommunications 650 to assemble the controlled list 610 of applicationsfrom the list 609 of all applications that can be installed on thevehicle. Typically building the list 610 from the list 609 involvesvalidation of the applications from a technical standpoint and/or abusiness standpoint of the provider.

The provider also sends communications 651 to select applications fromthe controlled list 610 to be installed on a particular vehicle. Theseselections may be based on a mapping a vehicle models to applications,for example. These selections 652 fed into the download directory 239.

Regarding the list of all available applications 609, it should beunderstood that this list can be assembled by applications developed bythe provider and/or third parties. In the case of third partiesproviding applications, the third party uses the application submission618 portion of the web portal 604 (which is hosted by a web serveroperated by the provider in one example) to submit an application 649 tobe included in the list 609.

A vehicle user can also select applications to be included in thedownload directory 239 using a computing terminal 626, for example usingany internet accessible computing device such as the mobile device or adesktop computer. The computing terminal 626 accesses the applicationselection portion 628 of the user web portal 605 (which is hosted by aweb server operated by the provider in one example) to view thecontrolled list 610 of applications that can be installed on hisvehicle. The user can then send communications 661 to selectapplications from the controlled list 610 that the user would likeinstalled on his vehicle. These selections 662 are fed into the downloaddirectory 239.

The user web portal 605 can also be configured to allow a user to removeparticular applications from the download directory 239, e.g. the usermay desire to remove one of the provider selected applications 652 addedto the download directory 239 via the provider. Removal can be bydeletion of an application already sent to the directory 239 or byindicating that a particular application is not desired before suchapplication is ever added to the download directory 239.

According to the above, applications can be accumulated into theper-vehicle download directory 239. At vehicle power-up, suchapplications can be downloaded and installed onto the vehicle. Thedownload directory 239 can then accumulate new applications until a nextvehicle power up.

It should be understood that an interface similar to that of the webportal 605 can be displayed on the head unit of the vehicle. The usercould then make selections from such interface for selectingapplications from the controlled list 610. The selected applicationscould be downloaded immediately to the vehicle instead of being put inthe download directory when the selections are made from the interface.

FIG. 7 illustrates a system to select and distribute applications to avehicle in a safe and intelligent manner according to user preferences.

One difference between the previously discussed system of FIG. 1 and thesystem of FIG. 7 is the install location for applications. Whereas theapplications A-C in the system 100 of FIG. 1 are installed and operatingon the mobile phone 20 (using the head unit 21 or other interfacepowered by the vehicle as an extended interface), the applicationsM-P/Q-S in the system 300 of FIG. 7 are installed on the head unit 321or other component powered by the vehicle. In system 300 of FIG. 7, thesoftware 330-332 enables a provider to select which applications can beinstalled on the head unit 321 and control distribution of the selectedapplications to the vehicle.

Before discussing the details of system 300 in detail in the followingparagraphs, it should be apparent that the structures and functions ofsystems 100 and 200 described in FIGS. 1-6 can be combined with thestructures and functions of system 300 (FIGS. 7-8) into a single system.For example, a single system could include some applications installedon a mobile phone using an interface of a vehicle as an extendedinterface and some applications installed on a component of the vehicle.

FIG. 8 illustrates a flow chart showing operation of the software ofFIG. 7.

In block 801, the head unit 321 communicatively couples to a mobiledevice such as mobile phone 320. In one example, the connection 540 isestablished via Bluetooth pairing of the head unit 321 and the mobilephone 320. The Bluetooth pairing can be in response to the vehicle beingpowered up (causing the head unit to power up and search for a Bluetoothdevice), although it should be apparent that Bluetooth pairing couldresult from other circumstances such as the mobile phone 320 poweringup, the mobile phone 320 being brought within range of the head unit321, re-pairing after another Bluetooth device is disconnected from thehead unit 321, etc. In other examples, the communicative connection canbe established by a user connecting the mobile phone 320 to the headunit 321 using a USB connection.

In block 802, the control software 330 accesses a telephone number ofthe mobile phone 320. It should be understood that mobile phones areactivated with a particular phone number in conjunction with subscribingto a call plan, which is the phone number the control software 330 readsfrom the mobile phone 320. In one example, the signaling 542 to obtainthe phone number is performed using Bluetooth signaling.

In block 803, the control software 330 sends signaling 543 to the server322. The signaling 543 can be sent over a local connection such as aUSB, Bluetooth, or WiFi connection to be relayed by the mobile device320 over a wireless telecommunications network. The content of thesignaling 543 can be similar to the signal 244 described in more detailpreviously with respect to FIG. 4, but in addition, can provide theobtained phone number.

In block 804, the control software 332 compares the phone numberincluded in the signaling 543 to the mapping 350. The mapping correlateseach of a plurality of download directories A-B accessible via thisparticular head unit 321 to a particular phone number. For example, inthe mapping a first phone number is correlated with the downloaddirectory A and a second phone number is correlated with the downloaddirectory B. The control software 332 selects one of the downloaddirectories A-B based on the comparison of the received telephone numberto the mapping 350.

The software 332 then checks the selected one of the downloaddirectories A-B to determine if there are any applications currentlystored in the selected directory. A scheme for intelligently selectingapplications that are present in the download directories A-B will bediscussed in detail later with reference to FIG. 9. For now, let it beassumed for the purposes of illustration that the download directories339A and 339B currently include applications 340A (M-P) and 340B (Q-S),respectively, in addition to the head unit frontend configurations 369Aand 369B.

As noted briefly in the previous paragraph, the download directories A-Binclude head unit frontend configurations A-B, respectively, in additionto the applications 340A and 340B. The configurations A-B can be storedas HTML code or other web code compatible with the web code renderer ofthe 399. Depending on which one of the head unit frontend configurationsA-B is downloaded to the head unit 321, a display 380 of the head unit321 will display a different graphical user interface. Each of thedifferent web code files 369A and 369B will produce a differentgraphical user interface when displayed using the display 380 and therenderer 399. For example, each graphical user interface could have itsown user customized settings such as a particular wallpaper selected bya user. A scheme for generating the different head unit frontendconfigurations A-B will be discussed in detail later with reference toFIG. 9.

In block 805, the software 332 generates and sends signaling to causethe IP gateway software 331 on the mobile phone 320 to operate as an IPgateway for forwarding applications to the head unit 321 similar to thescheme described in FIG. 4. In one example, similar to FIG. 4, suchsignaling includes communications to dynamically load the mobile phone320 with the software 331 to cause the software 331 to operate thereonfor the download to vehicle. This signaling may not take place if themobile phone 320 is already loaded with the software 331 and ready forIP gateway operation. In other examples, the signaling 345 couldoriginate from the control software 330 on the head unit 321 after theconnection 540 is established.

In block 806, the software 332 generates and sends IP packets 545 todownload the data from the selected one of the directories onto thevehicle, e.g. either applications M-P and configuration A orapplications Q-S and configuration B. The IP packets 545 are received bythe mobile phone 320 and forwarded by operation of the software 331 tothe head unit 321. It should be understood that in this particularillustration the IP packets 545 include both applications and aconfiguration for the graphical user interface, but in other scenariosthe IP packets 545 might contain either an application or aconfiguration. Also, it should be apparent that, if there are noapplications currently in the selected download directory and there havebeen no changes to the configurations stored in the download directorysince a previous download, then the IP packets 545 may not be sent.

In block 807, the software 330 receives the IP packets 545 and installsthe applications included therein on the vehicle (installation can be oncomponents of the head unit 321 or other vehicle components). Thesoftware 330 also processes the configuration from the IP packets 545using the web code renderer 399 to generate a particular graphical userinterface based on the detected phone number.

Thereafter, the graphical user interface output via the display 380 willcorrespond to one of the configurations A-B stored in the selecteddownload directory. A user of the vehicle can operate the installedapplications M-P or Q-S using the head unit 321 as an interface.

It should be understood that the software 330 and 332 can operateaccording to any of the principles described in FIGS. 1-3. For example,the software 330 and 332 can regulate utilization of the I/O resourcesof the head unit 321 by the active application(s) according to currentvehicle status. As another example, in systems where applications areinstalled on both the vehicle and a mobile device, the software 330 and332 can include all applications that utilize the vehicle interface inan application ranking/priority table similar to the table 13 (FIG. 1).

In the example described above, the control software 330 accesses aphone number of the mobile phone 320 to uniquely identify the mobilephone 320 from other mobile phones. In other examples, control softwareon the head unit 321 can access a different value on a communicativelycoupled mobile phone to uniquely identify the mobile phone from othermobile phones. Other examples of values can include, but are not limitedto, a physical address of the mobile phone. In such other examples, itshould be apparent that such values are used in the mapping, e.g. if theother values are physical addresses then the mapping includes physicaladdresses correlated to download directories.

In the example described above, the control software 330 sends theaccessed unique identifier (phone number in this example) to the server322. In other examples, the mapping 350 can be stored on the vehicle. Insuch a case, the control software 330 identifies a particular downloaddirectory listed in the mapping according to the comparison and sends anidentifier specifying the particular download to the server 322. Theserver 322 may then respond with IP packets 545 sending data from theidentified download directory.

FIG. 9 illustrates more detail of the system shown in FIGS. 7-8.

It was previously explained that the server 322 includes a plurality ofdownload directories 339A-B of applications waiting to be downloaded.FIG. 9 illustrates the user web portal 905 that can be involved increating the download directories 339A-B and selection of theapplications on a per-directory basis and describes an example use ofthis web portal 905.

A vehicle user can create a plurality of profiles corresponding to thevehicle using the profile creation portion 930 of the user web portal905. A profile can be created for each person that may use the vehicle.A field 927 requests a unique phone number or other unique identifier ofa mobile phone respectively corresponding to each person. A name of eachperson or other information for each person may be gathered with thephone number(s). After or during profile creation, server 322 creates adownload directory for each profile and updates the mapping 350 for eachnumber/directory combination. In some examples, the portion 930 can beconfigured to allow a user to rank the created profiles so that, if thehead unit can be coupled to more than one of the mobile devicessimultaneously (it can depend on the connection protocol whether this ispossible), a higher ranked one of the corresponding profiles will beused.

During or after profile creation the web portal 905 can be operated toselect applications to be included in the download directories 339A-Busing a computing terminal 926, for example using any interne accessiblecomputing device such as the mobile device or a desktop computer. Thecomputing terminal 926 accesses the application selection portion 928 ofthe user web portal 905 (which is hosted by a web server operated by theprovider in one example) to view the controlled list of applicationsthat can be installed on the vehicle. The user can then sendcommunications 961 to select applications from the controlled list thatthe user would like installed on his vehicle on a per-directory basis.These selections 962 are respectively fed into the download directories339A-B on a per-directory basis.

The user web portal 905 can also be configured to allow a user to removeparticular applications from the download directories 339A-B, e.g. theuser may desire to remove one of the provider selected applications 952added to the download directory 339A or 339B via the provider on aper-directory basis. Removal can be by deletion of an applicationalready sent to the download directory 339A or 339B, or by indicatingthat a particular application is not desired before such application isever added to the download directory 339A or 339B.

The user web portal 905 can also include a head unit frontendconfiguration customization portion 928. This portion 928 allows newconfigurations 369A-B to be added to the download directories 339A-B,with each person's configuration customized according to their requests.For example, a first wallpaper background can be added to the downloaddirectory 339A and a second different wallpaper background can be addedto the download directory 339B. Other customizations can includecustomized graphical interface buttons, customized graphical userinterface layout, custom images, etc.

According to the above, applications can be accumulated into theper-vehicle download directories 339A-B on a per-directory basis. Uponthe head unit coupling to a particular one of the mobile devices, datafrom a corresponding one of the download directories 339A-B can bedownloaded and installed onto the vehicle to provide a customizedapplication set and a customized user interface.

It should be understood that an interface similar to that of the webportal 905 can be displayed on the head unit of the vehicle. The usercould then make selections from such interface for selectingapplications from the controlled list. The selected applications couldbe downloaded immediately to the vehicle instead of being put in thedownload directory when the selections are made from the interface.

FIG. 10 illustrates a system to select a head unit graphical interfaceaccording to a configuration of the head unit.

The system 1000 includes a server 1022 and a head unit 1021 that caninclude components similar to any of the previously described serversand head units. It should be appreciated that the server 1022 and thehead unit 1021 communicate using a mobile device (not shown) that iscoupled to the head unit 1021. The head unit 1021 includes controlsoftware 1030 and the server 1022 includes control software 1032.

The software 1032 identifies a configuration of the head unit 1021, forexample, by probing 1081 the head unit 1021 to collect information. Thesoftware 1030 responds 1082 with information identifying theconfiguration of the head unit 1021. The response 1082 can include atleast one of the following: a make/model/year of the vehicle, apredefined code, or an ad hoc listing of the configuration of the headunit 1021 (such as color/monochrome display, native resolution, etc.)

The software 1032 then selects from a plurality of graphical userinterfaces based on the head unit information 1082. For example, if thehead unit information 1082 includes a predefined code, the software 1032can compare the code to a stored mapping 1085 of codes to graphical userinterfaces Y-Z. The selected graphical user interface corresponds to aparticular configuration of the head unit 1021 as reported by theinformation 1082. For example, if the head unit 1021 has a monochromedisplay, the selected Graphical User Interface (GUI) may be interface Y,whereas if the head unit 1021 has a color display, the selected GUI maybe interface Z. Or, perhaps if the head unit 1021 has a nativeresolution of a first value, the selected GUI may be interface Y,whereas if the head unit 1021 has a native resolution of a second value,the selected GUI may be interface Z. If the make/model/year of the carindicates an interior of a first design, say a luxury motif, theselected GUI may be interface Y, whereas if the make/model/year of thecar indicates an interior of a second design, say a sporty motif, theselected GUI may be interface Z.

Once a graphical user interface has been selected, the software 1032conducts an IP packet transfer 1045 of the selected one of the graphicaluser interfaces Y-Z. It should be understood that the IP packet transfer1045 may utilize the previously-described IP gateway software of themobile phone (not shown). The software 1030 automatically installs thereceived graphical user interface. The selected graphical user interfacecan replace a default graphical user inference 1090 or previouslydownloaded graphical user interface residing on the head unit 1021 priorto the transfer 1045.

It should be understood that the previously described frontendconfigurations can be applied to the selected and installed GUI. Forexample, a selected GUI can be installed on the head unit 1021, and thenfurther modified in appearance based on a customized frontend selectionaccording to a telephone number of the mobile device currently coupledto the head unit 1021.

FIG. 11 illustrates a system to generate and send remote computingapprovals to the head unit.

The system 1100 includes a server 1122 and a head unit 1121 that caninclude components similar to any of the previously described serversand head units. It should be appreciated that the server 1122 and thehead unit 1121 communicate using a mobile device 1131. The head unit1121 includes control software 1130 and the server 1122 includes controlsoftware 1132.

The head unit 1121 includes a remote desktop viewing program such as aVirtual Network Computing (VNC®) client 1148 to connect to the VNCserver 1149 running on the mobile device 1131. By way of background, aVNC client and server communicate to display the server's desktop orother current view on the client's display. The human interfacesdevice(s) directly connected to the client, e.g. keyboard, mouse, etc.,can then be used in conjunction with the displayed image to remotelycontrol the computing device running the VNC server. If an applicationis running in full screen mode on the computing device with the VNCserver, then the computing device with the VNC server controls thatapplication (rather than the entire desktop).

The control software 1130 receives a request 1155 from the mobile device1131 specifying a particular application X (1140). The control software1130 identifies the application identifier corresponding to the request1155 either by extracting the identifier itself from the request 1155 orusing a lookup based on information gleaned from the request or from anycommunication with the mobile device 1131. The control software 1130sends the communication 1156 containing the application identifier.

The control software 1132 compares the application identifier to aninternal table and generates a VNC approval 1157 for the application X.The VNC approval 1157 specifies the particular conditions under whichVNC is approved in conjunction for this application X. For example, ifthe application X is a navigation application, the approval 1157 mightspecify that VNC is approved when the vehicle is stopped or moving. Incontrast, if the application X is a media creation application, theapproval 1157 might specify that VNC is approved only when the vehicleis stopped.

The VNC approval 1157 can also specify different approvals based onwhether the application is currently running in full screen mode orwindowed mode. For example, the navigation application might be approvedwhen the vehicle is moving, but only as long as the navigationapplication is running on the mobile device 1131 in full screen mode.This will prevent VNC functionality immediately if the user switches thenavigation application into windowed mode while the vehicle is moving.

The VNC approval 1157 can also specify telephone numbers. For example,VNC can be permitted when the mobile device 1131 is running a mediaplayer application, but only if the mobile device has a particulartelephone number (this can be used as a form of parental control).

The control software 1130 stores the received VNC approval 1157 in adatabase 1135 of VNC approvals. The control software 1130 continuouslymonitors conditions based on the VNC approvals stored in the database1135 to generate the control signal 1160. The control signal 1160controls whether a view 1161 of the mobile device 1131 can be currentlydisplayed on a display of the head unit 1121 by the VNC client 1148. Thecontrol signal 1160 also controls whether inputs made using an inputinterface of the head unit 1121 will be sent 1162 to the VNC server1149.

FIG. 12 illustrates a system to push graphical user interface updates tothe head unit in response to the mobile device generating a request fora new application or the user web portal selecting a new application.

The system 1200 includes a server 1222 and a head unit 1221 that caninclude components similar to any of the previously described serversand head units. It should be appreciated that the server 1222 and thehead unit 1221 communicate using a mobile device 1231.

The server 1222 can receive an indication of a new application to beused in the system 1200 in at least two different forms (the term newapplication refers to an application that has not previously beendownloaded to the head unit 1221 and/or utilized the head unit 1221 asan extended interface). In one form, the mobile device 1231 sends anindication of a new application X (1240) to utilize the head unit 1221as an extended interface. More specifically, this indication is anapproval request 1271 generated and sent by the control software 1230 inresponse to receiving a request 1270 from the mobile device 1231.

Another way the server 1222 can receive an indication of a newapplication is from control over the user web portal 1205. The user webportal 1205 is similar to the previously described web portals. Using anapplication selection tool 1228, a user can use any remote computer toselect applications to be included in a corresponding download directory(not shown) for installation on the head unit. Thus, a receivedselection 1274 including a new application is another form of indicationof a new application to be used in the system 1200.

In response to detecting such an indication, the control software 1232determines whether to transmit an IP packet transfer 1245 including agraphical user interface update for the new application X. It should beapparent that no such IP packet transfer will be sent if the newapplication X is not included in the previously discussed controlledlist of applications (FIG. 6). In one example, the graphical userinterface update modifies a previously selected and installed graphicaluser interface (FIG. 10) to add an icon for accessing the newapplication X. In another example, the graphical user interface updateincludes any other form of update to a previously selected and installedgraphical user interface for operating new application X. The controlsoftware 1230 automatically installs the update in response to thesending of the request 1270 and/or the selections 1274. It should beapparent that the transfer 1245 can be included with a download of theapplication itself in the case that the download is waiting for vehiclepower up in a download directory.

FIG. 13A illustrates a flow chart showing pre-operation of a parentalcontrol scheme.

In block 1301, the server designates at least one profile as beingsubject to parental control. This profile can be selected by the accountholding, for example, by marking a selection using the web portal.

In block 1302, the server receives a login for a user designated as aparent (typically the account holder) for the profile subject toparental control. In block 1303, the server causes a list ofapplications associated with the profile subject to parental control tobe displayed using the web portal.

In block 1304, after displaying the list, the server receives selectionsfrom the displayed list. The server may store these selections in theprofile that is subject to parental control. The selections can includeapplications from the list and/or more detailed information in the caseof a conditional approval (a conditional approval is discussed later inmore detail).

FIG. 13B illustrates a flow chart showing operation of the parentalcontrol scheme.

In block 1320, in response to a mobile phone communicatively couplingwith the head unit, the head unit obtains a telephone number of themobile phone to be used to communicate with the server. In block 1321,the head unit sends the phone number to the server for analysis. If theobtained phone number does not match a profile designated as subject toparental control, then the parental control process completes in block1322.

Otherwise, if the obtained phone number does correspond to the profilesubject to parental control, then in block 1323 the server executesparental control. In one example, such execution includes blocks1323-1327, similar to the VNC approval process, discussed in the nextparagraph.

In block 1323, the server transmits a parental control message to thehead unit. In block 1324, the head unit continuously monitors conditionsbased on the parental control message. In block 1325, the head unitblocks a particular application from using the head unit as an extendedinterface and/or blocks a particular application installed on the headunit from running. For example, the head unit might receive anindication that the particular mobile phone has received a telephonecall, but then block the use of the head unit as an extended interfacefor the telephone call. Or, the head unit might block an attempt to runa media player application on the head unit in another example. Thecontinuous monitoring may be facilitated by a database on the head unitstoring received parental control messages.

In block 1326, the head unit conditionally blocks a particularapplication from using the head unit as an extended interface and/orrunning directly on the head unit. For example, the head unit mightreceive an indication that the particular mobile phone has received atelephone call, but then block the use of the head unit as an extendedinterface conditionally based on a value of a caller ID field on theincoming call. More specifically, the parental control message mightdesignate certain telephone numbers as exceptions to preventing the headunit from providing an extended interface for the telephone. The headunit obtains the caller ID value from the mobile phone and blocks themobile phone from utilizing an interface of the head unit conditionally.In another example, the head unit might block an applicationconditionally based on a condition of the vehicle, e.g. the head unitblocks the mobile phone from utilizing an interface of the head unitonly if the vehicle is currently moving.

In block 1327, the head unit does not block the particular applicationif the application is permitted according to the parental controlmessage. In this case, the head unit allows the application to operateaccording to approval by the server, e.g. according to whether theapplication is on the controlled list (FIG. 6).

It should be apparent that, in other examples, a system can enforce aparental control scheme using different processes than thosespecifically described above. For example, in another example, theprocesses of blocks 1323-1327 are not used. Instead, the head unitcontinuously reports conditions and application requests to the server,which dynamically withdraws a current approval according to the parentalcontrol settings. The server then controls the head unit to block acurrent disapproved application.

It will be obvious to those having skill in the art that many changesmay be made to the details of the above-described embodiments withoutdeparting from the underlying principles of the invention. The scope ofthe present invention should, therefore, be determined only by thefollowing claims.

Most of the equipment discussed above comprises hardware and associatedsoftware. For example, the typical navigation device is likely toinclude one or more processors and software executable on thoseprocessors to carry out the operations described. We use the termsoftware herein in its commonly understood sense to refer to programs orroutines (subroutines, objects, plug-ins, etc.), as well as data, usableby a machine or processor. As is well known, computer programs generallycomprise instructions that are stored in machine-readable orcomputer-readable storage media. Some embodiments of the presentinvention may include executable programs or instructions that arestored in machine-readable or computer-readable storage media, such as adigital memory. We do not imply that a “computer” in the conventionalsense is required in any particular embodiment. For example, variousprocessors, embedded or otherwise, may be used in equipment such as thecomponents described herein.

Memory for storing software again is well known. In some embodiments,memory associated with a given processor may be stored in the samephysical device as the processor (“on-board” memory); for example, RAMor FLASH memory disposed within an integrated circuit microprocessor orthe like. In other examples, the memory comprises an independent device,such as an external disk drive, storage array, or portable FLASH keyfob. In such cases, the memory becomes “associated” with the digitalprocessor when the two are operatively coupled together, or incommunication with each other, for example by an I/O port, networkconnection, etc. such that the processor can read a file stored on thememory. Associated memory may be “read only” by design (ROM) or byvirtue of permission settings, or not. Other examples include but arenot limited to WORM, EPROM, EEPROM, FLASH, etc. Those technologies oftenare implemented in solid state semiconductor devices. Other memories maycomprise moving parts, such as a conventional rotating disk drive. Allsuch memories are “machine readable” or “computer-readable” and may beused to store executable instructions for implementing the functionsdescribed herein.

A “software product” refers to a memory device in which a series ofexecutable instructions are stored in a machine-readable form so that asuitable machine or processor, with appropriate access to the softwareproduct, can execute the instructions to carry out a process implementedby the instructions. Software products are sometimes used to distributesoftware. Any type of machine-readable memory, including withoutlimitation those summarized above, may be used to make a softwareproduct. That said, it is also known that software can be distributedvia electronic transmission (“download”), in which case there typicallywill be a corresponding software product at the transmitting end of thetransmission, or the receiving end, or both.

Having described and illustrated the principles of the invention in apreferred embodiment thereof, it should be apparent that the inventionmay be modified in arrangement and detail without departing from suchprinciples. We claim all modifications and variations coming within thespirit and scope of the following claims.

1. A computer-implemented method for remotely managing user applicationprograms executable in a motor vehicle, the method comprising the stepsof: maintaining a list of available user application programs; approvingat least one of the available user application programs for use in aspecified motor vehicle make and model, wherein said approval isdetermined by or on behalf of the vehicle OEM or service providers;forming a controlled list of applications that identifies the approvedapplications; selecting at least one application from the controlledlist of approved applications for download to a specific motor vehicle,wherein said selection is made by or on behalf of an owner of thespecific motor vehicle; wirelessly downloading the selected applicationprogram to the specific motor vehicle; installing the downloadedapplication program for operation on a head unit of the specific motorvehicle wherein the application selecting step is carried out by a uservia application selection software executed on a user web portal orexecuted on the head unit of the motor vehicle; providing a servercomputer located remotely from the motor vehicle and having access towireless communications for exchanging information with the motorvehicle; implementing a plurality of download directories in the servercomputer, and storing in each download directory a corresponding set ofapplication programs selected by a corresponding user; receiving asignal from the motor vehicle, the signal including a phone number of auser mobile phone detected in the motor vehicle; and associating thereceived phone number to a corresponding one of the download directoriesin the server computer; wherein the wirelessly downloading stepcomprises downloading the selected set of application programs from thecorresponding download directory to the motor vehicle.
 2. The method ofclaim 1 wherein the wirelessly downloading step is automaticallyexecuted in the server responsive to a control signal from the motorvehicle, the control signal triggered by power-up of the motor vehicleor responsive to recognition of a user mobile wireless device in themotor vehicle.
 3. The method of claim 1 and further comprising: in atleast one download directory, storing a corresponding head unit frontendconfiguration; wherein the wirelessly downloading step comprisesdownloading the head unit frontend configuration from the correspondingdownload directory to the motor vehicle for modifying a user interfaceof the vehicle head unit.
 4. The method of claim 1 and furthercomprising: configuring the user mobile phone to provide an IP gateway;wherein said wirelessly downloading step comprises downloading theselected set of application programs from the corresponding downloaddirectory to the motor vehicle via the mobile phone IP gateway.
 5. Themethod of claim 4 and further wherein said configuring the user mobilephone to provide the IP gateway includes downloading IP gateway softwareto the mobile phone from the server.
 6. The method of claim 4 andfurther wherein the wirelessly downloading step comprises downloadingthe head unit frontend configuration from the corresponding downloaddirectory to the motor vehicle via the mobile phone IP gateway.
 7. Themethod of claim 1 and further wherein the signal from the motor vehicleis sent over a local connection from the head unit to the mobile phoneand relayed by the mobile phone over a wireless telecommunicationsnetwork to the server.
 8. A motor vehicle head unit comprising: adisplay screen; a processor; and a non-volatile machine-readable mediastoring instructions that, if executed in the processor, implement thefollowing components: a) control software arranged for communicationbetween the head unit and a remote server; b) a user applicationprogram; and c) interface code for communicating with a mobile phone inthe vehicle; wherein the control software includes code for acquiring aunique identifier from a mobile phone in the vehicle via the interfacecode; and further includes: code for transmitting a signal to the remoteserver, the signal including the unique identifier acquired from themobile phone to enable the remote server to select a particular one of aplurality of user profiles, user download directories, or head unitfrontend configurations based on a value of the unique identifieracquired from the mobile phone; wherein the unique identifier comprisesat least one of a mobile telephone number, device ID number, serialnumber, short range wireless protocol identifier, IP address; and codefor receiving, in response to transmitting the signal, and incomingcommunication originating from the remote server and based on theselected user profile, user download directory, or head unit frontendconfiguration.
 9. The head unit of claim 8 wherein the unique identifiercomprises the mobile telephone number of the mobile phone.
 10. The headunit of claim 8 wherein the control software implements communicationwith the server via an IP gateway provided by the mobile phone, or viaan on-board wireless network access device.
 11. The head unit of claim10 wherein the control software downloads the user application programfrom the server over the IP gateway provided by the mobile phone. 12.The head unit of claim 10 wherein the control software downloads theselected head unit frontend configuration from the server and appliesthe selected head unit frontend configuration to select or customize agraphical user interface rendered on the display screen.
 13. Acomputer-implemented method for remotely managing user applicationprograms executable in a motor vehicle, the method comprising the stepsof: providing a server computer located remotely from the motor vehicleand having access to wireless communications arranged for exchanginginformation with the motor vehicle; storing a digital configuration filein a datastore accessible to the server computer, the digitalconfiguration file including at least one user profile for a particularmotor vehicle, the user profile including a unique identifier of amobile phone associated with a potential driver of the motor vehicle;storing an indicator in the user profile to subject the correspondingdriver to parental control; receiving at the server computer awirelessly transmitted message from the vehicle, the message includingidentification of the motor vehicle and a unique identifier of a mobilephone detected in the vehicle; comparing the received message to theconfiguration files to find a user profile that matches the mobile phoneunique identifier; and if a matching user profile is found and itindicates that it is subject to parental control, wirelesslytransmitting a parental control message to the motor vehicle to controluse of user application programs in the vehicle based on the matchinguser profile; wherein the unique identifier of the mobile phonecomprises at least one of a mobile telephone number, device ID number,serial number, short range wireless protocol identifier, IP address. 14.The method of claim 3 wherein the matching user profile identifies atleast one application program to be blocked from utilizing a head unitas an extended user interface, and the transmitted parental controlmessage includes identification of the application program to be blockedfrom utilizing the head unit as an extended user interface.
 15. Themethod of claim 13 wherein the matching user profile identifies at leastone application program to be blocked from utilizing a head unit as anextended user interface under certain vehicle operating conditions, andthe transmitted parental control message includes identification of theapplication program, to be conditionally blocked from utilizing the headunit as an extended user interface, and the specific vehicle operatingconditions under which it is to be blocked.
 16. The method of claim 13wherein the matching user profile identifies at least one applicationprogram to be blocked from running on a head unit, and the transmittedparental control message includes identification of the applicationprogram to be blocked from running on the head unit.
 17. The method ofclaim 13 wherein application programs to be blocked under parentalcontrol are selected by an authorized account user accessing the serverthrough a user portal.